Internet session initiation on personal cellular telecommunications devices, and customization protocol therefor

ABSTRACT

A customizable client application capable of running on all seven classes of Internet-enabled personal cellular telecommunications devices whose Internet browser launching capabilities range from being Class 0 non Internet-enabled to Class 6 automatic Internet browser launching. The client application facilitates minimum subscriber intervention for Internet session initiation from an Internet session option of an interactive display message.

FIELD OF THE INVENTION

The invention in the field of mobile cellular telecommunications ingeneral, and Internet session initiation on personal cellulartelecommunications devices in particular, and a customization protocoltherefor.

BACKGROUND OF THE INVENTION

In Applicant's WO 01/52558 A2 entitled “Method for Operating a CellularTelecommunications Network, and Method for operating a Personal CellularTelecommunications Device” and WO 01/52572 A1 entitled “Method forOperating a Cellular Telecommunications Network”, the contents of whichare incorporated herein by reference, there is illustrated and describeda screen saver application for displaying display messages on personalcellular telecommunications devices in a screen saver like manner,namely, their display is temporarily interrupted during, say, a voicecall, an Internet session, and the like. The display messages arepreferably so-called “interactive display messages” in the sense that asubscriber can automatically activate a Point-To-Point (PTP)transmission response mechanism from a dedicated response meansintegrally provided in a display message. Interactive display messagesare preferably transmitted over a Point-To-MultiPoint (PTMP)transmission capability as opposed to over a PTP transmission capabilitydue to bandwidth constraints, server constraints, and the like. But itis envisaged that certain typically high value content, for example,financial highlights, traffic news, and the like, will be transmitted toselected subscribers over a PTP transmission capability.

With the advent of Internet-enabled personal cellular telecommunicationsdevices (hereinafter referred to as “Internet-enabled devices”), aninteractive display message typically includes inter alia an Internetsession option. However, the installed base of personal cellulartelecommunications devices include both non Internet-enabled devices andInternet-enabled devices having different Internet browser launchingcapabilities for setting up an Internet session. Moreover, many personalcellular telecommunications device cannot be directly interrogated by aclient application, for example, Applicant's screen saver application,for determining their Internet browser launching capability, therebyprecluding the provisioning of a universally supported clientapplication on the installed base of personal cellulartelecommunications devices. Furthermore, matters are still furthercomplicated since in some personal cellular telecommunications devicesclient applications run on a replaceable smart card residing in a MobileEquipment (ME). Thus, implementing a client application, for example,Applicant's screen saver application, on the installed base of personalcellular telecommunications devices requires solving severe problems,and all the more so when interactive display messages are transmittedover a PTMP transmission capability.

EP 0 685 972 entitled “Mobile Communication System and Method Therefor”and WO 99/41931 entitled “Server Request including Code for CustomizingService to Requesting Mobile Station” both illustrate and describeharmonization procedures for harmonizing service to a personal cellulartelecommunications device as provided by a mobile cellulartelecommunications network operator commensurate with the feature setsupported by the personal cellular telecommunications device. In EP 0685 972, a network initiates a handshake with a personal cellulartelecommunications device whereby the latter enables a feature of itsfeature set if supported by the network. In WO 99/41931, a personaltelecommunications device initiates a request for service includingidentification information, and the resulting service to the personalcellular telecommunications device is commensurate with its feature setas determined by its identification information.

SUMMARY OF THE INVENTION

For the purpose of the present invention, personal cellulartelecommunications device are classified in terms of their Internetbrowser launching capabilities into seven classes as follows:

Class 0 Internet-enabled devices which are in fact non-Internet enabled.

Class 1 Internet-enabled devices which require the time consuming andcumbersome input of the text (Uniform Resource Locator) URL of a Webpage into an Internet browser's address field before it can be launchedto the Web page.

Class 2 Internet-enabled devices which support Over The Air (OTA)Internet browser settings stored as Bookmarks whereby, on configurationof a new Bookmark, a subscriber can launch his Internet browser to theWeb page designated in the new Bookmark stored as either the Internetbrowser's default home page or a standard bookmark.

Class 3 Internet-enabled devices which support a so-called pushcapability whereby, on receipt of a data message with the text URL of aWeb page embedded therein, a subscriber can launch his Internet browserfrom the data message to the Web page.

Class 4 Internet-enabled devices which support a more aggressive pushcapability than a Class 3 Internet-enabled device insofar that anInternet browser is automatically launched to the Web page on receipt ofa data message with the text URL of a Web page embedded therein.

To date, Class 3 and 4 Internet-enabled devices are only WAP enabled,however, it is expected that similar push capabilities will beprovisioned in other technologies. In the case of a Class 3 WAP-enableddevice, the data message is known as a Service Indication (SI) Messagewhilst in the case of a Class 4 WAP-enabled device, the data message isknown as a Service Load (SL) message.

Class 5 Internet-enabled devices which support a so-called URLrecognition capability, for example, as implemented in Ericsson's R320phone whereby, on receipt of a SMS for display of the text URL of a Webpage, subscriber activation of the text URL launches his Internetbrowser to the Web page.

Class 6 Internet-enabled devices which support automatic Internetbrowser launching to a Web page by an application through a standardApplication Program Interface (API). In particular, support of a SAT(SIM Application Toolkit) pro-active Launch Browser command standardizedunder 3GPP's Technical Standard (TS) 31.111 entitled “3^(rd) GenerationPartnership Project; Technical Specification Group Terminals; USIMApplication Toolkit (USAT)” renders an exemplary Class 6Internet-enabled device enabling Internet sessions. ME support of theSAT pro-active Launch Browser command is indicated in an informationfield of a so-called Terminal Profile downloaded from a host ME to asmart card under a Profile Download procedure also standardized in theabovementioned TS.

Generally speaking, the present invention is for a customizable clientapplication capable of running on all seven classes of Internet-enabledpersonal cellular telecommunications devices whose Internet browserlaunching capabilities range from being Class 0 non Internet-enabled toClass 6 automatic Internet browser launching. The client applicationfacilitates minimum subscriber intervention for Internet sessioninitiation from an Internet session option of an interactive displaymessage, and in the case of Class 0 non Internet-enabled devices, anInternet session option is preferably deleted from a menu of PTPtransmission response mechanism options of an interactive displaymessage. The interactive display messages preferably include the fulltext URL of a target Web page destination to facilitate efficientInternet browser launching. However, in the case of a particularly longURL, for example,http://www.amazon.con/exec/obidos/wishlist/ref=nwl_shopping/103-2947502-5237400for launching to amazon.com's wish list page, the target Web pagedestination is preferably a Web page at a proxy Website, for example,http://www.celltick.com/000134 where 000134 specifies the Web page. TheWeb page at the proxy Website can either duplicate the true target Webpage destination, in this case, amazon.com's wish list page, or it canautomatically reroute an Internet browser thereto.

The customization is preferably achieved by way of a customizationprotocol suitable for providing details regarding a wide range offeatures of the feature set of an Internet-enabled device other than itsInternet browser launching capability, for example, screen size, and thelike. The customization protocol is implementable since all MEs areprovided as a matter of course with a unique vendor allocatedidentification numbers, for example, a GSM/DCS/PCS personal cellulartelecommunications device's 15 digit International Mobile EquipmentIdentification (IMEI) number. An ME's identification number can beemployed for interrogating an Equipment Technical Specification Register(ETSR) typically sorted by ME configuration types in terns of hardwareand software release as applicable to a population of at least two MEs,and typically numbering several tens of thousands of MEs, and upwards.Moreover, the ME configuration types are preferably not vendor specificbut rather cut across the model lines of two or more ME vendors wherebytwo or more ME models of different ME vendors may have the same MEconfiguration type.

Thus, the customization protocol can be employed for supplementing anexisting Terminal Profile, for example, as standardized under theaforementioned standard, and also for obtaining information regarding ahost ME which is already included in a Terminal Profile but which isknown to be inaccurate. Since newer MEs typically download a morecomprehensive Terminal Profile than older MEs, the same clientapplication may need to request more information about the feature setof an earlier ME than a newer ME. Typically, a client application onlyrequests information regarding its host ME once regardless of its hostME's powering down and Up.

Looking to the future, it is envisaged that each ME will be provided byits vendor with an industry recognized ME Configuration Type Number forspecifying its configuration type, thereby precluding the need for anintermediate step before interrogation of the ETSR. Similarly, it isenvisaged that in time each personal cellular telecommunications devicewill be provisioned with an information field indicating its class ofInternet browser launching capability.

The personal cellular telecommunications devices can include a widerange of mobile handheld devices including inter alia simple phones,Smartphones, Communicators, Wireless Information Devices (WIDs), and thelike, and dual technology devices, for example, including a GSMtransceiver and a Bluetooth transceiver. The client applications can bedeveloped under different industry wide and proprietary developmentenvironments, and can run on different Operating Systems (O/Ss)including inter alia Microsoft CE, Symbian EPOC, Palm O/S, and the like.Also, the present invention applies to all mobile Internet basedtechnologies including inter alia HTML, Compact HTML, WAP, and others.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to understand the present invention and to see how it can becarried out in practice, preferred embodiments will now be described, byway of non-limiting examples only, with reference to the accompanyingdrawings, in which similar parts are likewise numbered, and in which:

FIG. 1 shows a schematic representation of a GSM mobile cellulartelecommunications network for supporting a customizable clientapplication for WAP session initiation from interactive display messagesdisplayed on WAP-enabled devices;

FIG. 2 shows a portion of an ME Configuration Type Conversion Register(MECTCR) for identifying the ME configuration type of a WAP-enableddevice on the basis of a portion of its IMEI.number;

FIG. 3 shows a record of an Equipment Technical Specification Register(ETSR) specifying technical information in respect of a particular MEconfiguration type;

FIG. 4 shows a record of an Equipment Identification Register (EIR)listing IMEI numbers against their corresponding IMSI numbers;

FIG. 5 shows a record of an interactive display message for display on aWAP-enabled device;

FIG. 6 is a flow diagram of a customization protocol for thecustomization of a customizable client application;

FIG. 7 is a flow diagram of WAP session initiation on each of sevenclasses of WAP-enabled devices; and

FIGS. 8A-8J are pictorial representations of display screens displayedon different classes of WAP-enabled devices.

DETAILED DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a GSM cellular telecommunications network 1 for enablingWAP session initiation from a WAP-enabled device 2 in general, and fromWAP session option dedicated response means of interactive displaymessages displayed thereon in particular. The WAP-enabled device 2 has aMS-ISDN mobile telephone associated therewith, and includes a hostMobile Equipment (ME) 3, and a resident Subscriber Identity Module (SIM)card 4 capable of running SIM Toolkit applications (constituting clientapplications). The host ME 3 has its own unique vendor allocated 15digit International Mobile Equipment Identification (IMEI) number 6, forexample, 490548400308362, including four fields as follows: a six digitType Approval Code (TAC), a two digit Final Assembly Code (FAC), a sixdigit Phone Serial Number, and a single digit Additional Number. The SIMcard 4 has a cellular operator allocated 15 digit International MobileSubscriber Identity (IMSI) number 7, for example, 425010100437187. TheWAP-enabled device 2 has a WAP browser with a default WAP home pageand/or one or more Bookmark WAP pages (a default WAP home page or aBookmark WAP page both constituting a predefined Web page destination).The WAP-enabled device 2 may also have a cache memory for storing thefirst received content for each of one or more URLs, namely, its homepage, and the like. The cache memory is responsive to one or morecommands which may be embedded in such content, for example, not tocache content, to immediately delete content, and the like.

For the purpose of customization of a customizable client application,the network 1 includes two registers as follows: First, a MEConfiguration Type Conversion Register (MECTCR) 8 for determining the MEconfiguration type of a particular host ME from its FAC and Phone SerialNumber (see FIG. 2). And second, an Equipment Technical SpecificationRegister (ETSR) 9 sorted by ME Configuration Type Number and covering awide range of past and currently available ME configuration types (seeFIG. 3). The ETSR 9 includes technical information in various forms,called a feature set, and including inter alia YES/NO information fieldsin respect of certain features, for example, a host ME's WAP browserlaunching capability; numerical values in respect of other features, forexample, screen size; text; and the like. For illustrative purposes,FIG. 3 shows that the ME configuration type 10 is a Class 4 typeWAP-enabled device (Feature 1), and has a 30.times.40 screen size(Feature 16). Optionally, the customization protocol may employ anexisting Equipment Identification Register (EIR) 11 listing all the MEsin the installed base of personal cellular telecommunications devices bytheir IMEI numbers, and their corresponding SIM cards by their IMSInumbers for monitoring purposes, for example, for barring service tostolen equipment (see FIG. 4).

For the purpose of enabling WAP browser launching from an interactivedisplay message with a WAP session option dedicated response means, thenetwork 1 includes an application server 12 including a database forstoring records of interactive display messages (see FIG. 5), a ShortMessage Service Center (SMSC) 13, a WAP gateway 14 to the Internet cloudincluding an Active Server Page (ASP) site 15 for effecting a WAPwalkaround for use by Class 1 WAP-enabled devices 2, and a WAP pushgateway 16 for use by Class 3 and Class 4 WAP-enabled devices 2. Thenetwork 1 includes a dynamic database 17 for listing subscribers whohave activated WAP session option dedicated response means, and the textURLs of the target Web page destinations of their WAP browsers. The WAPgateway 14 includes a dynamic buffer 18 similar to the dynamic database17 but for listing all subscribers engaging in active WAP sessions, andthe text URLs of the actual Web page destinations of their WAP browsers.Each subscriber engaged in a WAP session is typically listed by hisMS-ISDN but alternatively other identification numbers associated withhis WAP-enabled device 2 may be used.

FIG. 5 shows that each record of an interactive display field containsthe following fields:

-   -   First, a Message Identification field denoted MSG ID for        uniquely identifying an interactive display message;        -   Second, a Message Type field denoted MSG TYPE for specifying            a Point-To-MultiPoint (PTMP) type message or a            Point-To-Point (PTP) type message and in the case that an            interactive display message is of the PTP type, its record            also includes a field containing details of the subscribers            to which the interactive display message is to be            transmitted (not shown);        -   Third, a CONTENT field containing the content to be            displayed on a WAP-enabled device;    -   And lastly, a RESPONSE OPTIONS field listing the PTP        transmission response mechanisms options of the interactive        display message including the text URL of a target WAP page        destination, and optionally, a voice call, an SMS, and the like.

The operation of the GSM mobile cellular telecommunications network isnow described in respect of each class of the seven classes ofWAP-enabled devices for an interactive display message (see FIG. 8A)offering a WAP session option to read the full story about Spielberg'snew film (see FIG. 8B) at a WAP page http://www.newvspielbergfilm.com.In accordance with its prevailing Profile Download procedure, forexample, ETSI GSM 11.14 entitled “Digital cellular telecommunicationssystem; Specification of the SIM Application Toolkit for the SubscriberIdentity Module—Module Equipment (SIM-ME) interface”, the abovementioned3GPP TS 31.111, and the like, the Terminal Profile is downloaded fromthe host ME 3 to the SIM card 4. In the case that the WAP-enabled device2 is a Class 6 WAP-enabled device, the SIM card 4 would be accordinglydownloaded that the ME 3 supports the pro-active Launch Browser commandstandardized under the abovementioned 3GPP TS 31.111. In the case thatthe WAP-enabled device 2 is not a Class 6 WAP-enabled device, then acustomization protocol is then initiated to determine its WAP browserlaunching capability, if any.

To determine a host ME's WAP browser launching capability and also sayits screen size, a client application running on the SIM card 4 directlydownloads its host ME's IMEI number 490548400308362 therefrom, andproceeds to strip off its TAC prefix and its Additional Number suffix toleave the ME configuration type distinguishing information 40030836which is sufficient to uniquely identify its host ME's configurationtype. The client application uploads a query to the ETSR 9, the queryincluding the number 40030836, and an additional field specifyingFeatures (1) and (16). The ETSR 9 forwards the number 40030836 to theMECTCR 8 which returns to the ETSR 9 that the host ME belongs to MEconfiguration type 10. The ETSR 9 determines that the host ME is a Class4 type WAP-enabled device, and has a 30×40 screen size and returns thevalues 4 and 30×40 to the client application for its customization.Alternatively, the IMEI number 490548400308362 corresponding to the IMSInumber 425010100437187 can be obtained from the EIR 11.

Class 0 non-WAP-enabled device:

On receipt of the interactive display message at a Class 0 WAP-enableddevice, the WAP full story option is deleted from the menu of PTPtransmission response mechanism options to leave the first and the lastoptions only (see FIG. 8C). Alternatively, if the WAP full story optionis not deleted, then in the event that a subscriber activates the WAPfull story option, a NO WAP SERVICE AVAILABLE message is displayed (seeFIG. 8D).

Class 1 WAP-Enabled Device:

In the event that a subscriber activates the WAP full story option ofthe interactive display message on a Class 1 WAP-enabled device, ittransmits a SMS to the application server 12 which updates the dynamicdatabase 17 in respect of the subscriber, and the text URI, of the WAPfull story. At the same time, the subscriber is prompted to manuallylaunch his WAP browser to the ASP site 15 preferably stored as aBookmark, for example, labeled Orange Redirect (see FIG. 8E).Alternatively, the ASP site's URL can be stored as the WAP browser'sdefault WAP home page but more importantly it has no cache memoryassociated therewith such that his WAP browser is truly launched to theASP site 15 on each launching rather than merely retrieving content fromthe cache memory. In the meantime, the application server 12 readies theASP site 15 to load content to the subscriber's WAP browser including ahypertext link to the WAP full story and suitable commands to ensurethat the content is not permanently stored in his device's cache memory.The subscriber navigates to the main menu (see FIG. 8F) before launchinghis WAP browser to the ASP site 15. On loading the content from the ASPsite 15, his WAP browser automatically invokes the hypertext link forits redirection to the WAP full story, thereby rendering a so-called WAPwalkaround whilst, in the meantime, his WAP enabled device 2 informs thesubscriber that the WAP full story is being loaded (see FIG. 8G). In thecase that the subscriber launches his WAP browser to the ASP site 15after a predetermined timeout T since his activation of the WAP fullystory option, his WAP browser is typically redirected to a default WAPpage selected by his cellular operator or service provider, for example,his cellular operator's home page, a news portal, and the like.

Alternatively, a WAP walkaround can be achieved without the use of anASP site 15 by directly interfacing between the application server 12and the WAP gateway 14 for replacement of the text URL of the predefinedWAP page destination of the subscriber's WAP browser with that of theWAP full story at the WAP gateway itself 14 for diverting his WAPbrowser from its predefined WAP page destination to the WAP full story.As in the former WAP walkaround, in the case that the subscriberlaunches his WAP browser after the predetermined timeout, it is launchedto its default WAP home page destination as if the subscriber had neveractivated the WAP full story option from the interactive displaymessage.

Class 2 WAP-Enabled Device:

In the event that a subscriber activates the WAP full story option ofthe interactive display message on a Class 2 WAP-enabled device, ittransmits an OTA Bookmark setting message to itself with the target WAPpage destination embedded therein for inclusion as a Bookmark in the WAPbrowser. Upon acceptance of the Bookmark setting message (see FIG. 8H)and upon activating the Bookmark, its WAP browser is launched to the WAPfull story. Alternatively, the Class 2 WAP-enabled device can send a SMSto the application server 12 for invoking the OTA Bookmark settingmessage.

Class 3 WAP-Enabled Device:

In the event that a subscriber activates the WAP full story option ofthe interactive display message on a Class 3 WAP-enabled device, ittransmits a Service Indication (SI) data message to itself with thetarget WAP page destination embedded therein. Upon receipt of the SImessage, it is displayed (see FIG. 8I) and upon activating the retrievaloption, its WAP browser is launched to the WAP full story.Alternatively, the Class 3 WAP-enabled device can send a SMS to theapplication server 12 for invoking the SI message from the WAP pushgateway 16.

Class 4 WAP-Enabled Device:

In the event that a subscriber activates the WAP full story option ofthe interactive display message on a Class 4 WAP-enabled device, ittransmits a Service Load (SL) data message to itself with the target WAPpage destination embedded therein whereupon on its receipt, its WAPbrowser is automatically launched to the WAP full story. Alternatively,the Class 4 WAP-enabled device can send a SMS to the application server12 for invoking the SL message from the WAP push gateway 16.

Class 5 WAP-Enabled Device:

In the event that a subscriber activates the WAP full story option ofthe interactive display message on a Class 5 WAP-enabled device, ittransmits a SMS to itself for display of the text URL of the target WAPpage destination. Upon receipt of the SMS, the text URL is displayedtypically with an instruction to the subscriber (see FIG. 8J) and uponsubscriber activation of the text URL, his WAP browser is launched tothe WAP full story.

Class 6 WAP-Enabled Device:

In the event that a subscriber activates the WAP full story option ofthe interactive display message on a Class 6 WAP-enabled device, its WAPbrowser is automatically launched to the WAP full story.

While the invention has been described with respect to a limited numberof embodiments, it will be appreciated that many variations,modifications, and other applications of the invention can be madewithin the scope of the appended claims. For example, as will now beapparent from the above, albeit that Class 1, 2, 3, 4 and 5Internet-enabled devices differ in terms of their Internet browserlaunching capability, they are similar from the client side insofartheir Internet browser launching requires the transmission of anoutgoing data message. This being the case, rather than the provisioningof a customizable client application capable of running on all sevenclasses of Internet enabled devices, three versions of the clientapplication can be provided as follows: a version for Class 0Internet-enabled devices, a version for Class 1, 2, 3, 4, and 5Internet-enabled devices, and a version for Class 6 Internet-enableddevices. The outgoing data message could then include an informationfield uniquely identifying a subscriber's Internet-enabled device suchthat on receipt of a data message therefrom, the network could determinewhich its class and invoke the walkaround as applicable to Class 1Internet-enabled devices, or a suitable data message as applicable toClass 2, 3, 4, and 5 Internet-enabled devices.

1. A customization protocol for customizing a customizable clientapplication for use in association with a host Mobile Equipment (ME) ofa personal cellular telecommunications device of a set of devices, eachMobile Equipment (ME) having a device screen, internet browsercapability features and screen features, and each said device receivingcellular service from a service provider, the ME having a unique vendorallocated ME identification number, and at least one vendor allocated MEvalue relating to at least one feature of the ME, said at least onevendor allocated ME value being available for downloading to thecustomizable client application, each host ME supporting a singlefeature set of at least two different feature sets of features, a subsetof MEs of the set of MEs supporting the same feature set of features,the customization protocol comprising the steps of: (a) providing aservice provider managed Equipment Technical Specification Register(ETSR) for storing service provider allocated technical informationregarding a value of at least one feature of at least two differentfeature sets of features for each ME of the set of MEs, the ETSR beingavailable for independent interrogation by each device of the set ofdevices, each device hosting the customizable client application forhandling incoming messages including display messages for display on thedevice screen of the host ME; (b) automatically downloading from the MEto the customizable client application a vendor allocated ME value of atleast one feature of the ME; (c) at least partially initiallycustomizing the hosted customizable client application to its associatedhost ME based on said automatically downloaded vendor allocated MEvalue; (d) receiving by the ETSR a query from a device having said hostME, the query uniquely identifying said associated host ME, whereby theparticular values of at least some of the features of said host ME arerequested by interrogation of said ETSR based on said identification ofsaid associated host ME; (e) obtaining the requested values from theETSR using the identification of the associated host ME; and (f)downloading the obtained service provider allocated ETSR values to thedevice for assigning each downloaded service provider allocated ETSRvalue to the corresponding feature in the customizable clientapplication and for customizing the customizable client application withrespect to the downloaded service provider allocated ETSR values of itshost ME's said feature set of features, each downloaded service providerallocated ETSR value being assigned to a feature to which a vendorallocated ME value was not assigned during said at least initial partialcustomization and/or replacing a downloaded vendor allocated ME valueassigned to a feature during said at least initial partialcustomization, whereby the customizable client application is customizedby the service provider for the particular device hosting thecustomizable client application independent of how the device is to beused by its user such that the customized client application handlessome incoming messages differently in accordance with its customization,and whereby said customization is the same for each ME of a subset ofMEs that supports the same feature set of features and a differentsubset of MEs having a different feature set of features beingcustomized differently.
 2. The protocol according to claim 1 wherein aquery is uploaded by its associated telecommunications device regardlessof its associated ME's powering down and up.
 3. The protocol accordingto claim 1 wherein a query is uploaded by its associatedtelecommunications device once regardless of its associated originatingME's powering down and up.
 4. The protocol according to claim 1 whereina query is not uploaded on every user initiated non-customizationservice request.
 5. The protocol according to claim 1 wherein the ETSRstores technical information relating to feature sets of features by MEconfiguration type where at least one ME configuration type isapplicable to a population of at least two MEs, and said query includesat least a portion of its associated ME's unique vendor allocated MEidentification number for enabling an ME configuration type of itsassociated ME to be distinguished.
 6. The protocol according to claim 1wherein the ETSR stores technical information relating to feature setsof features by ME configuration type where at least one ME configurationtype is applicable to a population of at least two MEs, and said queryincludes a vendor allocated ME Configuration Type Number fordistinguishing an ME configuration type of its associated ME.
 7. Theprotocol according to claim 1 wherein a query determines its associatedME's Internet browser launching capability for customization of a clientapplication handling interactive display messages with an Internetsession option.
 8. The protocol according to claim 1 wherein a querydetermines its associated ME's screen size for customization of a clientapplication controlling the display of display messages thereon.
 9. Theprotocol as claimed in claim 1 wherein as a result of saidcustomization, the customized client application displays incomingdisplay messages differently in accordance with its customization. 10.The protocol according to claim 1 wherein the query determines theassociated ME's display features for customization of a clientapplication controlling the display of display messages thereon.
 11. Theprotocol according to claim 1 wherein said client application to becustomized obtains the identification code from the device hosting it;obtains access to the ETSR; and uploads the query to the ETSR.
 12. Acustomization protocol for customizing a customizable client applicationfor use in association with a host Mobile Equipment (ME) of each one ofa set of personal cellular telecommunication devices, each MobileEquipment (ME) having a device screen, internet browser capabilityfeatures and screen features, and the ME having a unique vendorallocated ME identification number, and at least one vendor allocated MEvalue relating to at least one feature of the ME, said at least onevendor allocated ME value being available for downloading to thecustomizable client application, the customizable client applicationhaving a plurality of individual customizable features that togetherwhen each is assigned a value can specify certain features of the hostME to the customizable client application, the devices belonging to aset of devices wherein each ME of the set of MEs supports a singlefeature set of at least two different feature sets of features, a subsetof MEs of the set of MEs supporting the same feature set of features,the customization protocol comprising the steps of: (a) providing acustomizable client application hosted on the device, the customizableclient application for handling incoming messages including displaymessages for display on the device screen, and having at least somefeatures to be assigned values to customize the customizable clientapplication to its respective host ME; (b) identifying the host ME tothe hosted customizable client application; (c) automaticallydownloading at least one vendor allocated ME value from the ME to thecustomizable client application for assigning a vendor allocated MEvalue to at least one feature thereof; (d) at least partially initiallyconfiguring the customizable client application to its host ME based onsaid at least one automatically downloaded vendor allocated ME value;(e) obtaining the identification code from the device hosting the clientapplication; (f) obtaining access to a service provider managedEquipment Technical Specification Register (ETSR) which stores serviceprovider allocated technical information regarding the values of thefeatures of each ME of the set of MEs, wherein the ETSR can beindependently interrogated by each device; (g) uploading a query fromone of the devices to the ETSR, the query including the uniqueidentification code of the associated ME; (h) obtaining the particularvalues of at least some of the features of said host ME by interrogationof said ETSR based on said identification of said associated host ME;(i) receiving by the querying device the requested ME values from theETSR; and (j) assigning each service provider allocated ETSR value tothe corresponding feature in the customizable client application, eachdownloaded service provider allocated ETSR values being assigned to afeature to which a vendor allocated ME value was not assigned duringsaid at least initial partial customization and/or replacing adownloaded vendor allocated ME value assigned to a feature during saidat least initial partial customization; whereby the customizable clientapplication is customized by the service provider for the particular MEof the device hosting the client application independent of the usage ofthe device by its user such that the customized client applicationhandles some incoming messages differently in accordance with itscustomization; and whereby said customization is the same for each ME ofa subset of MEs that supports the same feature set and a differentsubset of MEs having a different feature set being customizeddifferently.
 13. The protocol as claimed in claim 12 wherein as a resultof said customization, the customized client application displaysincoming display messages differently in accordance with itscustomization.
 14. The protocol according to claim 12 wherein the querydetermines the associated ME's Internet browser launching capability;and wherein as a result of said customization, the customized clientapplication handles interactive display messages with an Internetsession option in accordance with said customization.
 15. The protocolaccording to claim 12 wherein the query determines the associated ME'sdisplay features for customization of a client application controllingthe display of display messages thereon.
 16. The protocol according toclaim 12 wherein said client application to be customized obtains theidentification code from the device hosting it; obtains access to theETSR; and uploads the query to the ETSR.
 17. The protocol according toclaim 12 wherein a query is uploaded by its associatedtelecommunications device regardless of its associated ME's poweringdown and up.
 18. The protocol according to claim 12 wherein a query isuploaded by its associated telecommunications device once regardless ofits associated originating ME's powering down and up.
 19. The protocolaccording to claim 12 wherein a query is not uploaded on every userinitiated non-customization service request.
 20. The protocol accordingto claim 12 wherein the ETSR stores technical information relating tofeature sets of features by ME configuration type where at least one MEconfiguration type is applicable to a population of at least two MEs,and said query includes at least a portion of its associated ME's uniquevendor allocated ME identification number for enabling an MEconfiguration type of its associated ME to be distinguished.
 21. Theprotocol according to claim 12 wherein the ETSR stores technicalinformation relating to feature sets of features by ME configurationtype where at least one ME configuration type is applicable to apopulation of at least two MEs, and said query includes a vendorallocated ME Configuration Type Number for distinguishing an MEconfiguration type of its associated ME.
 22. The protocol according toclaim 12 wherein a query determines its associated ME's screen size forcustomization of a client application controlling the display of displaymessages thereon.